Remove the need to annually update speaker-mod feature #855
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This parameterizes the "make current speaker" and "make last year speaker" function calls and text so there's one less thing to update every year. It then also changes how speaker status works, so that we store actual speaker years in the DB, and only give the special 'speaker' badge to current-year speakers so we don't need to update them.
It also updates a few other other instances of relying on updating the current hardcoded year.
Might be nice to think about a UI to add speakers prior to the year-before-last, but very low priority.
Not tested yet, will ping when I've tested locally. No need to merge imminently, very low benefit from pushing this through quickly. Will want to manually test on the server, should just make sure the Azure Functions server time isn't messed up.
Also intentionally removes the year from the HTML title, it's fine to have that just be "Roguelike Celebration"